🔄 Request Action
The Request Action is used to handle incoming HTTP requests and trigger a workflow based on the request parameters. It allows detailed control over request structure, authentication, headers, and expected responses.
This action is essential for workflows that need to interact with external services, APIs, or frontend applications.
🧩 Configuration Overview
The Request Action configuration dialog is divided into several tabs to control every aspect of the HTTP request:
1. Request Basic Info
- Method: Select from
GET,POST,PUT,DELETE, etc. - Name: Provide a unique name for the request (required).
- Group: Assign this request to a group/category (required).
2. Params Tab
Configure the parameters your HTTP request can accept:
🧷 Query Params
| Key | Value | Description |
|---|---|---|
| Define URL parameters to be passed as part of the request. |
🔗 Path Variables
| Key | Value | Description |
|---|---|---|
Useful for dynamic routing like /user/:id. |
3. Authorization Tab
Specify how the request should be authenticated:
- No Auth – No authentication required.
- API Key – Send a static key in headers or query params.
- Bearer Token – Secure access using bearer tokens (commonly used in OAuth2).
- Basic Auth – Username/password authentication.
Example:
Type: Bearer Token
Token: abc123xyz
4. Headers Tab
Use headers to add metadata or required configurations to your request:
| Key | Value | Description |
|---|---|---|
| Content-Type | application/json | Specifies body type |
| Authorization | Bearer abc123 | API token |
5. Body Tab
Define the body of the request depending on its type:
- None – No body required (e.g., for
GETrequests). - Form-Data – Key/value pairs for forms.
- Raw – Send raw JSON, XML, or text.
- Files – Send file uploads.
Example: Raw JSON Body
{
"username": "john_doe",
"email": "john@example.com"
}
6. Response JSON Tab
Configure how the workflow should respond after execution.
- Status Code – Define expected HTTP response codes (e.g.,
200,404). - Response JSON – Define the JSON structure to be returned with each status.
Example:
200 OK– Returns:
{ "status": "success" }
✅ Use Cases
- Trigger workflows from third-party webhooks.
- Build REST endpoints for your automation logic.
- Accept dynamic form submissions and process them in real-time.
- Secure incoming requests using authentication mechanisms.
📌 Summary
The Request Action forms the entry point of any externally triggered workflow. With support for parameters, authentication, flexible body types, and structured responses, it empowers seamless integration with outside systems or clients.
Use this action to build responsive, secure, and structured API-driven workflows.